|
In the Java programming language, heap pollution is a situation that arises when a variable of a parameterized type refers to an object that is not of that parameterized type.〔(【引用サイトリンク】url=http://docs.oracle.com/javase/tutorial/java/generics/nonReifiableVarargsType.html#heap_pollution )〕 This situation is normally detected during compilation and indicated with an unchecked warning.〔 Later, during runtime heap pollution will often cause a ClassCastException. A source of heap pollution in Java arises from the fact that type arguments and variables are not reified at run-time. As a result, different parameterized types are implemented by the same class or interface at run time. Indeed, all invocations of a given generic type declaration share a single run-time implementation. This results in the possibility of heap pollution.〔 Under certain conditions, it is possible that a variable of a parameterized type refers to an object that is not of that parameterized type. The variable will always refer to an object that is an instance of a class that implements the parameterized type. Heap Pollution in a non-varargs context public class HeapPollutionDemo } ==Further reading== * * * * 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Heap pollution」の詳細全文を読む スポンサード リンク
|